Automatically syncing recordings between two or more content recording devices

ABSTRACT

This disclosure generally relates to systems and methods that facilitate synchronizing recordings between a plurality of content recording devices using embedded markers or metadata, and employing the synchronized recordings on a content recording device or a content server to present one or more of the synchronized recordings concurrently in a merged presentation or in a manner that allows for switching between recordings while maintaining synchronization.

TECHNICAL FIELD

This disclosure generally relates to systems and methods that facilitatesynchronizing recordings among a plurality of content recording devicesusing embedded markers or metadata, and employing the synchronizedrecordings on a content recording device or a content server to presentone or more of the synchronized recordings concurrently in a mergedpresentation or in a manner that allows for switching between recordingswhile maintaining synchronization.

BACKGROUND OF THE INVENTION

As mobile content recording devices have become ubiquitous, oftentimes,a common event is recorded concurrently by a plurality of device users.For example, during a concert, sports game or newsworthy event,respective attendees may record the event from different perspectives.However, the attendees may not be aware of the other device usersrecording the event, or if they are aware, don't have access to theirrecordings. Furthermore, even if they had access to the other users'recordings, they have to manually try to align the other users'recordings to their own recording of the event in order to view therecordings concurrently or merge them together.

SUMMARY

A simplified summary is provided herein to help enable a basic orgeneral understanding of various aspects of exemplary, non-limitingembodiments that follow in the more detailed description and theaccompanying drawings. This summary is not intended, however, as anextensive or exhaustive overview. Instead, the purpose of this summaryis to present some concepts related to some exemplary non-limitingembodiments in simplified form as a prelude to more detailed descriptionof the various embodiments that follow in the disclosure.

In accordance with a non-limiting implementation, input indicating asynchronized recording request is received by a content recording deviceincluding a processor, and in response to receiving the synchronizedrecording request: a synchronized recording relationship is establishedwith at least one other content recording device that includes temporalsynchronization between the content recording device and the at leastone other content recording device, at least one marker is inserted intoa recording being captured by the content recording device; and the atleast one other content recording device is instructed to insert atleast one other marker into the at least one other recording beingcaptured by the at least one other content recording device, wherein theat least one other marker is temporally synchronized with the at leastone marker.

In accordance with a non-limiting implementation, a content recordingdevice, comprises an interface component configured to receive inputindicating a synchronized recording request; and a content recordingcomponent configured to, in response to receiving the synchronizedrecording request: establish a synchronized recording relationship withat least one other content recording device that includes temporalsynchronization between the content recording device and the at leastone other content recording device; insert at least one marker into arecording being captured by the content recording device; and instructthe at least one other content recording device to insert at least oneother marker into the at least one other recording being captured by theat least one other content recording device, wherein the at least oneother marker is temporally synchronized with the at least one marker.

In accordance with another non-limiting implementation, a subset of aplurality of recordings having respective markers are accessed, whereinthe respective markers are temporally synchronized between the pluralityof recordings, and wherein the subset comprises at least two of theplurality of recordings; and the subset of recordings are timesynchronized based upon the respective markers.

In accordance with a further non-limiting implementation, a contentserver component is configured to access a subset of a plurality ofrecordings having respective markers, wherein the respective markers aretemporally synchronized between the plurality of recordings, and whereinthe subset comprises at least two of the plurality of recordings; and acontent synchronization component is configured to time synchronize thesubset of recordings based upon the respective markers.

These and other implementations and embodiments are described in moredetail below.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a block diagram of an exemplary non-limiting systemfor generating recordings in a synchronized manner amongst a pluralityof content recording devices in accordance with an implementation ofthis disclosure.

FIG. 2 illustrates a block diagram of an exemplary non-limiting contentrecording component that manages synchronized recording of content for acontent recording device in accordance with an implementation of thisdisclosure.

FIG. 3 illustrates a block diagram of an exemplary non-limiting devicesynchronization component that manages establishing of synchronizedrecording between content recording devices in accordance with animplementation of this disclosure.

FIG. 4 illustrates a block diagram of an exemplary non-limiting contentserver that can access and synchronize recordings in accordance with animplementation of this disclosure.

FIG. 5 illustrates a block diagram of an exemplary non-limiting contentsynchronization component that synchronizes content recordings receivedor accessed by a content server in accordance with an implementation ofthis disclosure.

FIG. 6A illustrates a block diagram of an exemplary non-limiting acontent recording device with a recording application displayed inaccordance with an implementation of this disclosure.

FIG. 6B illustrates a block diagram of an exemplary non-limiting contentrecording device with a recording application displayed after having aninitiate synchronized element selected in accordance with animplementation of this disclosure.

FIG. 6C illustrates a block diagram of an exemplary non-limiting contentrecording device with a recording application displayed having aselectable accept synch record request element and a selectable denysynch record request element in accordance with an implementation ofthis disclosure.

FIG. 6D illustrates a block diagram of an exemplary non-limiting contentrecording device with a recording application displayed having aselectable accept synch record request element and a selectable denysynch record request element in accordance with an implementation ofthis disclosure.

FIG. 7A illustrates a block diagram of an exemplary non-limiting tokenin accordance with an implementation of this disclosure.

FIG. 7B illustrates a block diagram of an exemplary non-limitingrespective views from recording applications in content recordingdevices focused on a different perspectives of a landscape scene inrelation to token initiated recording in accordance with animplementation of this disclosure.

FIG. 7C illustrates a block diagram of an exemplary non-limitingrespective views from recording applications in content recordingdevices focused on a stage from different locations at a concert eventin relation to token initiated recording in accordance with animplementation of this disclosure.

FIG. 8A illustrates a block diagram of an exemplary non-limitingsynchronized content generated using matching content recordings ofdifferent members of a band in accordance with an implementation of thisdisclosure.

FIG. 8B illustrates a block diagram of an exemplary non-limitingsynchronized content generated using matching content recordings oflandscape scene in accordance with an implementation of this disclosure.

FIGS. 9A-C illustrate block diagrams of an exemplary non-limiting windowthat allows for presenting matching content recordings and switchingamongst them at an equivalent point in time using a previous button andnext button in accordance with an implementation of this disclosure.

FIG. 10 illustrates an exemplary non-limiting flow diagram for a contentrecording device to establish a synchronized recording relationship withother content recording devices in accordance with an implementation ofthis disclosure.

FIG. 11 illustrates an exemplary non-limiting flow diagram for a contentrecording device to establish a synchronized recording relationship inaccordance with an implementation of this disclosure.

FIG. 12 illustrates an exemplary non-limiting flow diagram for a contentrecording device to initiate recording of content in accordance with animplementation of this disclosure.

FIG. 13 illustrates an exemplary non-limiting flow diagram for a contentrecording device to initiate recording of content using a token inaccordance with an implementation of this disclosure.

FIG. 14 illustrates a block diagram of an exemplary non-limitingnetworked environment in which the various embodiments can beimplemented.

FIG. 15 illustrates a block diagram of an exemplary non-limitingcomputing system or operating environment in which the variousembodiments can be implemented.

DETAILED DESCRIPTION

Overview

Various aspects or features of this disclosure are described withreference to the drawings, wherein like reference numerals are used torefer to like elements throughout. In this specification, numerousspecific details are set forth in order to provide a thoroughunderstanding of this disclosure. It should be understood, however, thatcertain aspects of this disclosure may be practiced without thesespecific details, or with other methods, components, materials, etc. Inother instances, well-known structures and devices are shown in blockdiagram form to facilitate describing this disclosure.

In situations in which systems and methods described here collectpersonal information about users, or may make use of personalinformation, the users can be provided with an opportunity to controlwhether programs or features collect user information (e.g., informationabout a user's social network, social actions or activities, profession,a user's preferences, or a user's current location), or to controlwhether or how to receive content from the content server that may bemore relevant to the user. In addition, certain data can be treated inone or more ways before it is stored or used, so that personallyidentifiable information is removed. For example, a user's identity canbe treated so that no personally identifiable information can bedetermined for the user, or a user's geographic location can begeneralized where location information is obtained (such as to a city,ZIP code, or state level), so that a particular location of a usercannot be determined. The user can add, delete, or modify informationabout the user. Thus, the user can control how information is collectedabout the user and used by a server.

In accordance with various disclosed aspects, a mechanism is providedfor a content recording device to interact with one or more othercontent recording devices to establish synchronized recording. Forexample, a user can be watching an event and enable a recordingapplication on a content recording device. The recording application canpresent the user with an option to initiate a synchronized recordingwith other content recording devices, for example, near the event andwithin wireless communication. The respective recordings of the contentrecording devices can have metadata or embedded markers added to allowfor synchronization of the recordings. Additionally, the contentrecording devices can interact with a content server to store respectiverecordings of the event. The content server can synchronize therecordings using the metadata or markers and present one or more of thesynchronized recordings, concurrently, in a merged presentation or in amanner that allows for switching between recordings while maintainingsynchronization.

Recording (or content) can include, for example, video, audio, image,text, or any combination thereof. Recordings can be available on anintranet, internet, or can be local content.

With reference to the embodiments described below, an example contentrecording device recording video content is presented for illustrativepurposes only. It is to be appreciated that any suitable type of contentcan be employed.

Content Recording Device

Referring now to the drawings, FIG. 1 depicts a system 100 forgenerating recordings in a synchronized manner amongst a plurality ofcontent recording devices 110. System 100 includes a plurality ofcontent recording devices 110 capable of recording content. System 100also includes content server 150 that can receive recordings from theplurality of content recording devices 110. While content server 150 isdepicted as a distinct device in this embodiment, it is to beappreciated that in another embodiment content recording device 110 canact as a content server 150 for one or more other content recordingdevices 110, thus not requiring a separate content server 150 device.Content recording device 110 also includes a content recording component120 that records content for content recording device 110 andestablishes synchronized recordings with other content recording devices110. In addition, content recording device 110 includes an interfacecomponent 130 that interacts with other content recording devices 110 orcontent server 150 to send and/or receive information related torecording content. Additionally, content recording device 110 includes acontent recording device data store 140 that can store content, as wellas, data generated or received by content recording device 110, contentrecording component 120, and interface component 130. Content recordingdevice data store 140 can be stored on any suitable type of storagedevice, non-limiting examples of which are illustrated with reference toFIGS. 14 and 15.

While only one content server 150 is shown, content recording device 110can interact with any suitable number of content servers 150concurrently. In addition, content recording device 110 can interactwith any suitable number of other content recording devices 110concurrently. Furthermore, content recording device 110 and contentserver 150 can respectively receive input from users to controlrecording, interaction with, and presentation of content and associatedinformation, for example, using input devices, non-limiting examples ofwhich can be found with reference to FIG. 15.

Content recording device 110 and content server 150, each respectivelyinclude a memory that stores computer executable components and aprocessor that executes the computer executable components stored in thememory, a non-limiting example of which can be found with reference toFIG. 15. Content recording device 110 can communicate via a wired and/orwireless network with content server 150 or other content recordingdevices 110.

Content recording device 120 can be any suitable type of device forrecording, interacting with, receiving, accessing, or supplying contentlocally, or remotely over a wired or wireless communication link,non-limiting examples of include a wearable device or a non-wearabledevice. Wearable device can include, for example, heads-up displayglasses, a monocle, eyeglasses, contact lens, sunglasses, a headset, avisor, a cap, a helmet, a mask, a headband, clothing, camera, videocamera, or any other suitable device capable of recording content thatcan be worn by a human or non-human user. Non-wearable device caninclude, for example, a mobile device, a mobile phone, a camera, acamcorder, a video camera, personal data assistant, laptop computer,tablet computer, desktop computer, server system, cable set top box,satellite set top box, cable modem, television set, monitor, mediaextender device, blu-ray device, DVD (digital versatile disc or digitalvideo disc) device, compact disc device, video game system, portablevideo game console, audio/video receiver, radio device, portable musicplayer, navigation system, car stereo, motion sensor, infrared sensor,or any other suitable device capable of recording content. Moreover,content recording device 110 and content server 150 can include a userinterface (e.g., a web browser or application), that can receive andpresent displays and content generated locally or remotely.

Referring to FIG. 2, content recording component 120 managessynchronized recording of content for content recording device 110.Content recording component 120 includes a user interface component 210that receives user input and presents displays related to initiating orterminating recording of content. For example, a user may be watching aconcert and enter or select a command via an input device that interactswith user interface component 210 to activate a recording application oncontent recording device 110. Content recording component 120 alsoincludes a device synchronization component 220 that managesestablishing of synchronized recording between content recording devices110, and initiation or termination of synchronized recordings. Inaddition, content recording component 120 includes a recording markercomponent 230 that generates one or more markers for synchronization ofrecordings on content recording devices 110. Furthermore, contentrecording component 120 includes a metadata component 240 that generatesmetadata for recordings on content recording device 110.

Content recording component 120, for example, can initiate recording ofcontent by receiving input to activate a recording application oncontent recording devices 110. In another example, the process ofrecording content can be activated automatically according to predefinedor user specified criteria. Referring to FIG. 6A, in accordance withnon-limiting example, a content recording device A 610 is depicted witha recording application 615A. Conventional elements of a recordingapplication are not shown as they are well known to those skilled in theart. Recording application 615A can present an initiate synchronizedrecording 640 element that is selectable to activate synchronizedrecording. User interface component 210 can recognize selection of theinitiate synchronized recording 640 element and instruct devicesynchronization component 220 to activate synchronized recording oncontent recording device 110.

Referring to FIG. 3, device synchronization component 220 includesdevice identification component 310 that identifies other contentrecording devices 110 to which a synchronized recording relationship canbe established. Device synchronization component 220 includes devicerecording connection component 320 that establishes a synchronizedrecording relationship with other content recording devices 110. Inaddition, device synchronization component 220 includes synchronizedrecording component 330 that manages synchronized recording with theother content recording devices 110 with which a synchronized recordingrelationship has been established. It is to be appreciated that theother content recording devices 110 can have a content recordingcomponent 120 that manages synchronized recording.

Device identification component 310 employs one or more wireless and/orwired connections to identify other content recording devices 110 towhich a synchronized recording relationship can be established. Forexample, a mobile phone can employ wireless communication, such asBluetooth, 802.11a/b/g/n, near field communication (NFC), Global Systemfor Mobile Communications (GSM), Code division multiple access (CDMA),General packet radio service (GPRS), Universal Mobile TelecommunicationsSystem (UMTS), Long Term Evolution (LTE), Enhanced Data rates for GSMEvolution (EDGE), Wideband Code Division Multiple Access (W-CDMA), TimeDivision Synchronous Code Division Multiple Access (TD-SCDMA), WorldwideInteroperability for Microwave Access (WiMAX), Long Term EvolutionAdvanced, Evolved High-Speed Packet Access, infrared, lightwave oroptical based standard, or any other suitable wireless communicationstandard, to identify content recording devices nearby. Deviceidentification component 310 can perform identification by applying oneor more predefined and/or user specified filters to the other contentrecording devices 110. In a non-limiting example, the filters caninclude geographical parameters (e.g. distance, global positioningcoordinates, city, or any other suitable geography based parameter),recording parameters (e.g., aspect ratio, resolution, color, frame rate,bit rate, encoding format, capture format, or any other suitableparameter associated with recording content), user relationshipparameter (e.g. social network connections, friends, family, coworkers,email contacts, or any other suitable parameter associated withestablished relationships amongst users), device type (e.g. such as thetype of content recording device), maximum number or devices toidentify, or any other suitable parameter that can be employed for apredefined or user specified filter. For example, a user can specifythat they only want to have other content recording devices 110identified that are within a threshold distance from their contentrecording device 110, are a friend of theirs in a social network, canrecord high definition 1080p content, and are using a mobile phone. Itis to be appreciated that device identification component 310 can rankthe identified other content recording devices 110 based upon predefinedor user specified ranking criteria. For example, a user can include afilter as indicated in the above example that further specifies to onlyidentify the top 10 other content recording devices 110 according toranking criteria that specifies closest distance. Additionally, weightscan be applied to filter parameters or ranking criteria. Referring toFIG. 6B, in a non-limiting example, content recording device A 610 isdepicted with recording application 615A displayed after having theinitiate synchronized recording 640 element selected. Deviceidentification component 310 on content recording device A 610 is shownto have identified three other content recording devices 110, DEVICE B,DEVICE C, and DEVICE D which are presented in recording application615A. While only three other content recording devices 110 areillustrated in this example, any suitable number of other contentrecording devices 110 can be presented with appropriate navigationcontrols. In an embodiment, DEVICE B, DEVICE C, and DEVICE D areselectable by a user of recording application 615A to indicate which ofthe other content recording devices 110 the user would like to establisha synchronized recording relationship. In this example, DEVICE B andDEVICE C are selected as indicated by the black box next to thosedevices in the display, and DEVICE D is not selected as indicated by thewhite box next to that device in the display. A selectable record 645element is also presented that the user can select once having chosenthe other content recording devices 110 which initiates device recordingconnection component 320 to attempt to establish a synchronizedrecording relationship with the selected other content recording devices110. It is to be appreciated that any suitable mechanism for presentingand selecting other content recording devices 110 can be employed. Inanother non-limiting example, device identification component 310 canautomatically attempt to establish a synchronized recording relationshipwith other content recording devices identified and/or selected.

Device recording connection component 320 communicates with contentrecording device B 620 and content recording device C 630 to attempt toestablish a synchronized recording relationship. Referring to FIG. 6C,content recording device B 620 is depicted with recording application615B having a selectable accept synch record request 650A element thatthe user can select to establish a synchronized recording relationshipwith the content recording device A 610, and a selectable deny synchrecord request 655A element that the user can select to preventestablishing a synchronized recording relationship with the contentrecording device 610A. In FIG. 6D, content recording device C 630 isdepicted with recording application 615C having a selectable acceptsynch record request 650B element that the user can select establish asynchronized recording relationship with the content recording device A610, and a selectable deny synch record request 655B element that theuser can select to prevent establishing a synchronized recordingrelationship with the content recording device A 610. It is to beappreciated that content recording device B 620 and content recordingdevice C 630 can also have predefined or user selectable permissionparameters that allow or restrict capabilities of content recordingdevice A 610 in the established synchronized recording relationship. Ina non-limiting example, permission parameters can include, automaticacceptance or denial of synchronized recording requests, recordingsettings (e.g. camera or camcorder visual or audio recording settings),recorded content access privileges, recorded content editing privileges,application access privileges, file transfer privileges, shared recordedcontent ownership privileges, recorded content distribution privileges,or any other suitable parameters associated with recording, accessing,editing, or distributing recorded content. For example, contentrecording device B 620 can have predefined permission settings thatrestrict content recording device A 610 from changing any settings oncontent recording device B 620 and further only allows content recordingdevice A 610 to access recorded content once transferred to contentserver 150. In another example, content recording device C 630 can havepredefined permission settings that allow content recording device A 610to change recording settings and access recorded content on contentrecording device C 630. In addition, once a synchronized recordingrelationship is established between a content recording device 110 andother content recording devices 110, a synchronized recordingrelationship can be established between the other content recordingdevices 110 automatically or manually. For example, once contentrecording device A 610 establishes a synchronized recording relationshipwith content recording device B 620 and content recording device C 630,a synchronized recording relationship can be established between contentrecording device B 620 and content recording device C 630. In anotherexample, content recording device B 620 and content recording device C630 would need to establish a synchronized recording relationship witheach other manually. It is to be appreciated that any suitable mechanismfor establishing a synchronized recording relationship and permissionsbetween content recording devices 110 can be employed. Additionally,communication acknowledgement, retry, and timeout mechanisms betweencontent recording devices 110 can be employed when establishing asynchronized recording relationship. Furthermore, security mechanism canbe employed when establishing a synchronized recording relationshipbetween content recording devices 110, such as a password, a personalidentification number (PIN) code, a Bluetooth pairing based mechanism, akey based mechanism, a certificate based mechanism, or any othersuitable security mechanism.

Referring back to FIG. 3, synchronized recording component 330 caninitiate synchronized recording on content recording device 110 andother content recording devices 110 once a synchronized recordingrelationship has been established. It is to be appreciated that one ormore of content recording device 110 and other content recording devices110 can already be recording content. In a non-limiting example, wherecontent recording device 110 and other content recording devices 110 arenot currently recording content, synchronized recording component 330can instruct content recording device 110 and the other contentrecording devices 110 to initiate recording of content. In anothernon-limiting example, where one or more of content recording device 110and the other content recording devices 110 are already recordingcontent, synchronized recording component 330 instructs contentrecording device 110 or content recording devices 110 that are notcurrently recording content to initiate recording of content.

In another example, synchronized recording component 330 can employ atoken to initiate synchronized recording on content recording device 110and other content recording devices 110 once a synchronized recordingrelationship has been established. A token, in a non-limiting example,can be selected from a library or captured from an image or audiocapturing device, such as a particular object or audio signal. Forexample, a token can be an image of an object, such as a particularface, car set of characters, flower, etc., that is selected from aninternal or external image library, received from another device, orcaptured by a camera on content recording device 110. It is to beappreciated that any suitable object can be employed. In anotherexample, a token can be an audio signal, such as recording of aparticular voice, sound, or set of words, that is selected from aninternal or external audio library, received from another device, orcaptured by a microphone on content recording device 110. It is to beappreciated that any suitable audio signal can be employed. In anembodiment, synchronized recording component 330 can recognize the tokenby visual or audio input (e.g. using visual recognition, audiorecognition, or speech to text algorithms) and instruct contentrecording device 110 and other content recording devices 110 to initiaterecording content. For example, referring to FIG. 7A, in a non-limitingexample, token 720 of an image of a face is depicted. Referring to FIG.7B in a non-limiting example, respective views from recordingapplications in content recording devices 610, 620, and 630 focused on alandscape scene are illustrated. When synchronized recording component330 on content recording devices 610 recognizes token 720, it caninstruct content recording devices 610, 620, and 630 to initiaterecording content. This, for example, can be advantageous where contentrecording devices 610, 620, and 630 are employed for generating apanoramic recording when their respective content recordings arecombined.

In another embodiment, synchronized recording component 330 cancommunicate the token to other content recording devices 110. When eachof content recording device 110 and other content recording devices 110respectively recognizes the token by visual or audio input, they canrespectively initiate recording of content. For example, referring toFIG. 7C, is depicted, in a non-limiting example, respective views fromrecording applications in content recording devices 610, 620, and 630focused on a stage from different locations at a concert event. It is tobe appreciated that, in this example, the views depicted do not have tobe at the same time, but when the token 720 is within view of therespective content recording devices 610, 620, and 630. When respectivesynchronized recording components 330 on content recording devices 610,620, and 630 recognize token 720 (e.g. face of the guitar player), theycan instruct respective content recording devices 610, 620, and 630 toinitiate recording content. This, for example, can be advantageous whenthe object desired to be recorded, such as a guitar player roamingaround a stage, is moving in and out of view of respective contentrecording devices 110.

Respective content recordings on the content recording devices 110 canbe conveyed during or after recording to one or more of the contentrecording devices 110 in the established synchronized recordingrelationship. Furthermore, respective content recordings can be conveyedto content server 150.

Referring back to FIG. 2, recording marker component 230 generates oneor more markers for synchronization of recordings between contentrecording device 110 and other content recording devices 110 with whicha synchronized recording relationship has been established. For example,recording marker component 230 can generate one marker that iscommunicated to content recording device 110 and other content recordingdevices 110 with instructions to embed the marker in their respectiverecordings. In another example, recording marker component 230 cangenerate markers periodically that are communicated to content recordingdevice 110 and other content recording devices 110 with instructions toembed the markers in their respective recordings. For example, giventhat recordings on respective content recording devices 110 can beginand end at different times, periodic embedding of markers allows forincreasing points in time where respective recordings can besynchronized. In a non-limiting example, a marker can include, anaudible marker (e.g. an audible signal inserted into an audio portion ofthe recording), a visual marker (e.g. an visual element inserted into avisual portion of the recording), a code marker (e.g. programmatic codeinserted into the data stream/file of the recording), or any othersuitable mechanism that can be embedded in content recordings to allowfor synchronization between said content recordings. It is to beappreciated that multiple types of markers can be employed for a set ofsynchronized content recordings. For example, periodic embedding ofmarkers can cycle amongst audible marker, visual marker, or code marker.However, a marker meant for time synchronization at a common point intime between content recordings can be the same on each of the contentrecordings for later matching during playback or combining ofsynchronized content recordings.

Continuing with reference to FIG. 2, metadata component 240 generatesmetadata to associate with recordings on content recording device 110.It is to be appreciated that metadata can be automatically generatedusing artificial intelligence algorithms, using internal and externalinformation sources and devices by metadata component 240, manuallyspecified by a user associated with the recording, or using any suitableprocess for generating metadata. In a non-limiting example, metadata caninclude timestamps, source clock for timestamp, type of a user identityor account information associated with a user who recorded the content,user specified description of the recording, a type of content,geographic location information associated with the recording (e.g.,using global positioning system (GPS), cellular tower information,Internet Protocol location resolution, or any other suitablegeo-location mechanism), source of the content, type of device used togenerate the content, formatting process employed to generate thecontent, or filters applied to the content. Additionally, metadata caninclude video, audio, image, or text parameters of the content. In anon-limiting example, a video recording can include title, year,language, description, cast, parental rating, length, video format,resolution, aspect ratio, audio format, etc. In another non-limitingexample, a musical recording can include metadata such as source, title,artist, album, year, language, track genre, length, composer, lyrics,parental rating, album art, format, bit rate, sampling rate, bits persample, number of content streams, audio codec, etc. One skilled in theart would readily recognize that, based on the type of content, thereare well known metadata types that are conventionally associated.However, the information is not limited to only such traditionalmetadata types. Any suitable type of information can be associated withthe content as metadata. It is to be appreciated that other contentrecording devices 110 in the established synchronized recordingrelationship can also recorded metadata for their respective recordings.Furthermore, content recording device 110 can communicate metadata tothe other content recording devices 110 for association with theirrespective content recordings. In a non-limiting example, informationthat allows for identification of content recordings that were part ofan established synchronized recording relationship can be communicatedas metadata. The metadata can be employed by content server 150(described below), for example, to assist in locating or matchingcontent.

Respective content recording devices 110 can convey their contentrecordings and any information associated with their content recordingsto content server 150.

Content Server

Referring to FIG. 4, content server 150 includes content synchronizationcomponent 410 that synchronizes content recordings. In addition, contentserver 150 can include a device interface component 420 that interactswith content recording devices to send and/or receive informationrelated to content recordings. Additionally, content recording server120 includes a server data store 430 that can store content, as well as,data generated or received by content server 150, contentsynchronization component 410, and device interface component 420.Server data store 430 can be stored on any suitable type of storagedevice, non-limiting examples of which are illustrated with reference toFIGS. 14 and 15. Furthermore, while FIG. 4 depicts two content recordingdevices 110, any suitable number N, where N is an integer, of contentrecording devices 110 can interact with content server 150 concurrently.While content server 150 can interact directly with content recordingdevices 110 to receive content recordings, it is to be appreciated thatcontent server 150 does not need to interact with any content recordingdevices 110 to perform some functions described below. For example,content server 150 can access content recordings in a local library or aremote library not located on a content recording device 110 to performsynchronization on a subset of the content recordings. Moreover, contentserver 150 can also be a content recording device 110 as discussedabove.

Continuing with reference to FIG. 4, device interface component 420 canreceive content recordings from one or more content recording devices110. The content recordings can be received with specification ofpermissions, markers, metadata as discussed above, as well as any othersuitable information related to the content recordings. Furthermore,device interface component 420 can store the content recordingsaccording to the specified permissions, such as in global storagelocation or a specific account on the content server 150. Additionally,device interface component 420 can manage accessing, editing, ordistribution of the content recordings according to the specifiedpermissions.

Referring to FIG. 5, content synchronization component 410 synchronizescontent recordings received or accessed by content server 150. Contentsynchronization component 410 includes recording matching component 510that identifies matching content recordings. Content synchronizationcomponent 410 also includes server marker generation component 520 thatgenerates markers to embed in content recordings. In addition, contentsynchronization component 410 includes marker synchronization component530 that synchronizes markers between respective content recordings.Moreover, content synchronization component 410 includes synchronizedcontent generation component 540 that generates synchronized contentfrom a plurality of matching content recordings.

Recording matching component 510 can employ metadata associated with arecording or generate additional metadata in order to identify contentrecordings that are associated with a common event. For example,recording matching component 510 can compare metadata, such as by usingalgorithms, criteria, or thresholds, from content recording 1 withcontent recordings 2 through M, where M is an integer of 2 or greater,to determine if any of content recordings 2 through M are associatedwith a common event in content recording 1. In a non-limiting example,recording matching component 510 can determine if respective geographiclocations associated with content recordings are within a thresholddistance from each other, or if respective timestamps associated withcontent recordings are within a threshold time from each other, or ifrespective textual descriptions associated with a content recordingscontains common terms (e.g. location, artist name, venue, event name,etc.). It is to be appreciated that any metadata can be compared betweencontent recordings using any suitable matching mechanism. Furthermore,recording matching component 510 can analyze a content recording togenerate metadata to associate thereto. For example, recording matchingcomponent 510 can perform a visual analysis to recognize objects in theimages, such as people, faces, clothing, buildings, cars, a stage, avenue, road signs, or any other suitable visual object that can beemployed to generate metadata for content recording matching to a commonevent. In another example, recording matching component 510 can performan audio analysis to recognize audio signals, such as music, voices,vehicles, crowd cheers, city clock bell, or any other suitable soundthat can be employed to generate metadata for content recording matchingto a common event. It is to be appreciated that metadata can alsoinclude fingerprints generated from visual or audio analysis.

Continuing with reference to FIG. 5, server marker generation component520 can analyze a content recording to identify elements of therecording that can be used for time synchronization between contentrecordings. Server marker generation component 520 can employ visualanalysis to recognize objects in the frame images, such as people,faces, clothing, buildings, cars, a stage, a venue, road signs, or anyother suitable visual object that can be employed for content recordingtime synchronization. In addition, server marker generation component520 can estimate relative position of objects in relation to each otherin each frame. For example, in a recording of a concert event, theposition of a singer in the band in relation to the other members of theband, equipment, and a stage can be useful as a marker because analysisof another matching content recording can allow for identification of apoint in the other recording where the singer in the band is in the sameor within a threshold position relative to the other members of theband, equipment, and stage. Server marker generation component 520 canalso perform an audio analysis to recognize audio signals, such asmusic, voices, vehicles, crowd cheers, city clock bell, or any othersuitable sound that can be employed to generate metadata for contentrecording time synchronization. For example, a city clock bell ringingwould be useful as marker because audio analysis of another matchingcontent recording can allow for identification of the city clock bellringing in the other matching content recording. Server markergeneration component 520 can tag a content recording with respectivemarkers at locations in the recording where visual objects or audiosignals that can be used for time synchronization between contentrecordings.

Marker synchronization component 530 can compare markers betweenmatching content recordings to identify matching markers. For example,markers that were embedded by content recording devices 110 in anestablished synchronized recording relationship will have unique markersfor each common point in time to which a marker was embedded. As such,marker synchronization component 530 can easily identify unique markersfor each common point in time amongst matching content recordings fromcontent recording devices 110 in an established synchronized recordingrelationship. In another example, where all or some of the matchingcontent recordings are not from content recording devices 110 in anestablished synchronized recording relationship, matching of markerstagged by server marker generation component 520 can be performed. Forexample, audio or video analysis of the portions of the respectivematching content recordings associated with markers can be performedusing a suitable matching mechanism to identify matching portions of therespective matching content recordings. After identifying matchingmarkers or portions of respective matching content recordings, markersynchronization component 530 can perform time synchronization betweenmatching content recordings. For example, marker synchronizationcomponent 530 can determine respective time offset(s) between matchingmarkers or portions of respective pairs of matching content recordingsand associate the respective time offsets to the respective pairs of thematching content recordings. In another example, marker synchronizationcomponent 530 can normalize timestamps in matching content recordings toa common time reference, such as in a non-limiting example the contentserver 150 clock, based upon the determined time offsets. It is to beappreciated that any suitable mechanism for recording differences inclocks between matching content recordings or normalization oftimestamps in matching content recordings can be employed. Moreover,marker synchronization component 530 can also attempt to identifyoffsets in timestamps between matching content recordings, for example,using metadata defining a source clock for a timestamp. Comparing twosource clocks can allow for identification of on offset betweenrespective timestamps of two content recordings.

With continued reference to FIG. 5, synchronized content generationcomponent 540 can generate synchronized content from a plurality ofmatching content recordings. For example, matching content recordingswith normalized timestamps or associated time offsets can be temporallyaligned to create new synchronized content. FIG. 8A illustrates anexample synchronized content 810 generated using matching contentrecordings 815A, 815B, 815C of different members of a band. Thesynchronized content 810 concurrently depicts matching contentrecordings 815A, 815B, 815C in a time synchronized manner. FIG. 8Bdepicts an example synchronized content 820 generated using matchingcontent recordings 825A, 825B, 825C of a landscape scene. Thesynchronized content 820 is a panoramic video generated by stitchingtogether the time synchronized matching content recordings 825A, 825B,825C. In another example, not shown, time synchronized matching contentrecordings can be combined to form a three-dimensional video,three-dimensional video that can be rotated about an axis, a threedimensional video that can be rotated about a point omni-directionally,or any other suitable content that can be formed using time synchronizedmatching content recordings.

Furthermore, content synchronization component 410 can present matchingcontent recordings in a time synchronized manner without combining theminto newly generated synchronized content. For example, referring backto FIG. 8A., content synchronization component 410 can present matchingcontent recordings 815A, 815B, 815C using three separate windows (notshown) that run the respective matching content recordings in a timesynchronized manner. In another example, referring to FIGS. 9A-C,content synchronization component 410 can present a window 910 thatallows for presenting matching content recordings 815A, 815B, or 815Cand switching amongst them at an equivalent point in time using previousbutton 915 and next button 920. It is to be appreciated that anysuitable mechanism that allows for selection of which matching contentrecording 815A, 815B, or 815C to currently view in window 910 can beemployed.

FIGS. 10-13 illustrate various methods in accordance with certaindisclosed aspects. While, for purposes of simplicity of explanation, themethodologies are shown and described as a series of acts, it is to beunderstood and appreciated that the disclosed aspects are not limited bythe order of acts, as some acts may occur in different orders and/orconcurrently with other acts from that shown and described herein. Forexample, those skilled in the art will understand and appreciate that amethodology can alternatively be represented as a series of interrelatedstates or events, such as in a state diagram. Moreover, not allillustrated acts may be required to implement a methodology inaccordance with certain disclosed aspects. Additionally, it is to befurther appreciated that the methodologies disclosed hereinafter andthroughout this disclosure are capable of being stored on an article ofmanufacture to facilitate transporting and transferring suchmethodologies to computers.

Referring to FIG. 10, an exemplary method 1000 for a content recordingdevice 110 to establish a synchronized recording relationship with othercontent recording devices 110 is depicted. At reference numeral 1010, arequest to activate a synchronized recording is received (e.g., by auser interface component 210, device synchronization component 220,content recording component 120, or content recording device 110). Atreference numeral 1020, one or more other content recording devices 110with which a synchronized recording relationship can be established areidentified (e.g., by a device identification component 310, devicesynchronization component 220, content recording component 120, contentrecording device 110, or interface component 130). At reference numeral1030, a synchronized recording relationship is established with at leastone of the other content recording devices 110 (e.g., by a devicerecording connection component 320, device synchronization component220, content recording component 120, content recording device 110, orinterface component 130). At reference numeral 1040, synchronizedrecording is initiated amongst the content recording device 110 and theat least one other content recording device 110 in the establishedsynchronized recording relationship (e.g., by a synchronized recordingcomponent 330, device synchronization component 220, content recordingcomponent 120, content recording device 110, or interface component130). At reference numeral 1050, content recording device 110 recordscontent (e.g., by a synchronized recording component 330, devicesynchronization component 220, content recording component 120, orcontent recording device 110). At reference numeral 1060, the contentrecording device 110 and the at least one other content recording device110 in the established synchronized recording relationship areinstructed to embed at least one marker for time synchronization intotheir respective content recordings (e.g., by a synchronized recordingcomponent 330, device synchronization component 220, content recordingcomponent 120, content recording device 110, or interface component130). At reference numeral 1070, content recording device 110 embeds theat least one marker in its content recording (e.g., by a synchronizedrecording component 330, device synchronization component 220, contentrecording component 120, or content recording device 110). At referencenumeral 1080, content recording device 110 can perform an optional actof associating metadata with its content recording and/or instructionthe at least one other content recording device 110 in the establishedsynchronized recording relationship to associate metadata with theirrespective content recordings (e.g., by a synchronized recordingcomponent 330, device synchronization component 220, content recordingcomponent 120, content recording device 110, or interface component130). At reference numeral 1090, content recording device 110 canperform the optional act of conveying its content recording to contentserver 150, for example when content recording device 110 is not alsoperforming as content server 150. (e.g., by a synchronized recordingcomponent 330, device synchronization component 220, content recordingcomponent 120, content recording device 110, or interface component130).

Referring to FIG. 11, an exemplary method 1100 for a content recordingdevice 110 to establish a synchronized recording relationship isdepicted. At reference numeral 1110, a request to activate asynchronized recording is received (e.g., by a device recordingconnection component 320, device synchronization component 220, contentrecording component 120, content recording device 110, or interfacecomponent 130). At reference numeral 1120, a determination is madewhether to establish the synchronized recording relationship. (e.g., bya device recording connection component 320, device synchronizationcomponent 220, content recording component 120, content recording device110, or interface component 130). If the determination at 1120 is “NO”meaning that a determination has been made not to establish thesynchronized recording relationship, the method proceeds to element1135. If the determination at 1120 is “YES” meaning that a determinationhas been made to establish the synchronized recording relationship, themethod proceeds to element 1130. At reference numeral 1135, a responseis sent to the request denying the request (e.g., by a device recordingconnection component 320, device synchronization component 220, contentrecording component 120, content recording device 110, or interfacecomponent 130). At reference numeral 1130, a response is sent to therequest accepting the request and the synchronized recordingrelationship is established (e.g., by a device recording connectioncomponent 320, device synchronization component 220, content recordingcomponent 120, content recording device 110, or interface component130). At reference numeral 1140, instructions are received to initiatesynchronized recording of content (e.g., by device synchronizationcomponent 220, content recording component 120, content recording device110, interface component 130). At reference numeral 1150, content isrecorded (e.g., by device synchronization component 220, contentrecording component 120, or content recording device 110). At referencenumeral 1160, instructions are received to embed at least one marker fortime synchronization in the content recording (e.g., by devicesynchronization component 220, content recording component 120, contentrecording device 110, or interface component 130). At reference numeral1170, the at least one marker is embedded in content recording (e.g., bydevice synchronization component 220, content recording component 120,content recording device 110, or interface component 130). At referencenumeral 1180, an optional act can be performed of receiving orgenerating metadata and associating the metadata with the contentrecordings (e.g., by device synchronization component 220, contentrecording component 120, content recording device 110, or interfacecomponent 130). At reference numeral 1190, an optional act can beperformed of conveying the content recording to content server 150, forexample when content recording device 110 is not also performing ascontent server 150 (e.g., by device synchronization component 220,content recording component 120, content recording device 110, orinterface component 130).

Referring to FIG. 12, an exemplary method 1200 for a content recordingdevice 110 to initiate recording of content is depicted. At referencenumeral 1210, a token is generated or captured (e.g., by a devicesynchronization component 220, content recording component 120, orcontent recording device 110). At reference numeral 1220, the token isconveyed to other content recording devices 110 in an establishedsynchronized recording relationship with the content recording device110 (e.g., by a device synchronization component 220, content recordingcomponent 120, content recording device 110, or interface component130). At reference numeral 1230, a token is recognized (e.g., by adevice synchronization component 220, content recording component 120,or content recording device 110). At reference numeral 1240, recordingof content is initiated in response to recognizing the token (e.g., by adevice synchronization component 220, content recording component 120,or content recording device 110). At reference numeral 1250, an optionalact can be performed of instructing the other content recording devicesin an established synchronized recording relationship to initiaterecording of content (e.g., by a device synchronization component 220,content recording component 120, content recording device 110, orinterface component 130).

Referring to FIG. 13, an exemplary method 1300 for a content recordingdevice 110 to initiate recording of content using a token is depicted.At reference numeral 1310, content recordings are received or accessed(e.g., by a content synchronization component 410, content server 150,or device interface component 420). At reference numeral 1320, anoptional act can be performed of generating metadata for the contentrecordings (e.g., by a recording matching component 510, contentsynchronization component 410 or content server 150). At referencenumeral 1330, matching content recordings are identified (e.g., by arecording matching component 510, content synchronization component 410or content server 150). At reference numeral 1340, an optional act canbe performed of generating marker for time synchronization for one ormore of the matching content recordings (e.g., by a server markergeneration component 520, content synchronization component 410 orcontent server 150). At reference numeral 1350, respective markers ofthe matching content recordings are time synchronized (e.g., by a markersynchronization component 530, content synchronization component 410 orcontent server 150). At reference numeral 1360, a synchronized recordingis generated from at least two of the matching content recordings andtheir respective time synchronized markers (e.g., by a synchronizedcontent generation component 540, content synchronization component 410or content server 150).

Exemplary Networked and Distributed Environments

One of ordinary skill in the art can appreciate that the variousembodiments described herein can be implemented in connection with anycomputer or other client or server device, which can be deployed as partof a computer network or in a distributed computing environment, and canbe connected to any kind of data store where media may be found. In thisregard, the various embodiments described herein can be implemented inany computer system or environment having any number of memory orstorage units, and any number of applications and processes occurringacross any number of storage units. This includes, but is not limitedto, an environment with server computers and client computers deployedin a network environment or a distributed computing environment, havingremote or local storage.

Distributed computing provides sharing of computer resources andservices by communicative exchange among computing devices and systems.These resources and services include the exchange of information, cachestorage and disk storage for objects, such as files. These resources andservices can also include the sharing of processing power acrossmultiple processing units for load balancing, expansion of resources,specialization of processing, and the like. Distributed computing takesadvantage of network connectivity, allowing clients to leverage theircollective power to benefit the entire enterprise. In this regard, avariety of devices may have applications, objects or resources that mayparticipate in the various embodiments of this disclosure.

FIG. 14 provides a schematic diagram of an exemplary networked ordistributed computing environment. The distributed computing environmentcomprises computing objects 1410, 1412, etc. and computing objects ordevices 1420, 1422, 1424, 1426, 1428, etc., which may include programs,methods, data stores, programmable logic, etc., as represented byapplications 1430, 1432, 1434, 1436, 1438. It can be appreciated thatcomputing objects 1410, 1412, etc. and computing objects or devices1420, 1422, 1424, 1426, 1428, etc. may comprise different devices, suchas personal digital assistants (PDAs), audio/video devices, mobilephones, MP3 players, personal computers, laptops, tablets, etc.

Each computing object 1410, 1412, etc. and computing objects or devices1420, 1422, 1424, 1426, 1428, etc. can communicate with one or moreother computing objects 1410, 1412, etc. and computing objects ordevices 1420, 1422, 1424, 1426, 1428, etc. by way of the communicationsnetwork 1440, either directly or indirectly. Even though illustrated asa single element in FIG. 14, network 1440 may comprise other computingobjects and computing devices that provide services to the system ofFIG. 14, and/or may represent multiple interconnected networks, whichare not shown. Each computing object 1410, 1412, etc. or computingobjects or devices 1420, 1422, 1424, 1426, 1428, etc. can also containan application, such as applications 1430, 1432, 1434, 1436, 1438, thatmight make use of an API, or other object, software, firmware and/orhardware, suitable for communication with or implementation of variousembodiments of this disclosure.

There are a variety of systems, components, and network configurationsthat support distributed computing environments. For example, computingsystems can be connected together by wired or wireless systems, by localnetworks or widely distributed networks. Currently, many networks arecoupled to the Internet, which provides an infrastructure for widelydistributed computing and encompasses many different networks, thoughany suitable network infrastructure can be used for exemplarycommunications made incident to the systems as described in variousembodiments herein.

Thus, a host of network topologies and network infrastructures, such asclient/server, peer-to-peer, or hybrid architectures, can be utilized.The “client” is a member of a class or group that uses the services ofanother class or group. A client can be a computer process, e.g.,roughly a set of instructions or tasks, that requests a service providedby another program or process. A client process may utilize therequested service without having to “know” all working details about theother program or the service itself.

In a client/server architecture, particularly a networked system, aclient can be a computer that accesses shared network resources providedby another computer, e.g., a server. In the illustration of FIG. 14, asa non-limiting example, computing objects or devices 1420, 1422, 1424,1426, 1428, etc. can be thought of as clients and computing objects1410, 1412, etc. can be thought of as servers where computing objects1410, 1412, etc. provide data services, such as receiving data fromclient computing objects or devices 1420, 1422, 1424, 1426, 1428, etc.,storing of data, processing of data, transmitting data to clientcomputing objects or devices 1420, 1422, 1424, 1426, 1428, etc.,although any computer can be considered a client, a server, or both,depending on the circumstances. Any of these computing devices may beprocessing data, or requesting transaction services or tasks that mayimplicate the techniques for systems as described herein for one or moreembodiments.

A server is typically a remote computer system accessible over a remoteor local network, such as the Internet or wireless networkinfrastructures. The client process may be active in a first computersystem, and the server process may be active in a second computersystem, communicating with one another over a communications medium,thus providing distributed functionality and allowing multiple clientsto take advantage of the information-gathering capabilities of theserver. Any software objects utilized pursuant to the techniquesdescribed herein can be provided standalone, or distributed acrossmultiple computing devices or objects.

In a network environment in which the communications network/bus 1440 isthe Internet, for example, the computing objects 1410, 1412, etc. can beWeb servers, file servers, media servers, etc. with which the clientcomputing objects or devices 1420, 1422, 1424, 1426, 1428, etc.communicate via any of a number of known protocols, such as thehypertext transfer protocol (HTTP). Objects 1410, 1412, etc. may alsoserve as client computing objects or devices 1420, 1422, 1424, 1426,1428, etc., as may be characteristic of a distributed computingenvironment.

Exemplary Computing Device

As mentioned, advantageously, the techniques described herein can beapplied to any suitable device. It is to be understood, therefore, thathandheld, portable and other computing devices and computing objects ofall kinds are contemplated for use in connection with the variousembodiments. Accordingly, the computer described below in FIG. 15 is butone example of a computing device that can be employed with implementingone or more of the systems or methods shown and described in connectionwith FIGS. 1-13. Additionally, a suitable server can include one or moreaspects of the below computer, such as a media server or other mediamanagement server components.

Although not required, embodiments can partly be implemented via anoperating system, for use by a developer of services for a device orobject, and/or included within application software that operates toperform one or more functional aspects of the various embodimentsdescribed herein. Software may be described in the general context ofcomputer executable instructions, such as program modules, beingexecuted by one or more computers, such as client workstations, serversor other devices. Those skilled in the art will appreciate that computersystems have a variety of configurations and protocols that can be usedto communicate data, and thus, no particular configuration or protocolis to be considered limiting.

FIG. 15 thus illustrates an example of a suitable computing systemenvironment 1500 in which one or aspects of the embodiments describedherein can be implemented, although as made clear above, the computingsystem environment 1500 is only one example of a suitable computingenvironment and is not intended to suggest any limitation as to scope ofuse or functionality. Neither is the computing environment 1500 beinterpreted as having any dependency or requirement relating to any oneor combination of components illustrated in the exemplary operatingenvironment 1500.

With reference to FIG. 15, an exemplary computing device forimplementing one or more embodiments in the form of a computer 1510 isdepicted. Components of computer 1510 may include, but are not limitedto, a processing unit 1520, a system memory 1530, and a system bus 1522that couples various system components including the system memory tothe processing unit 1520.

Computer 1510 typically includes a variety of computer readable mediaand can be any available media that can be accessed by computer 1510.The system memory 1530 may include computer storage media in the form ofvolatile and/or nonvolatile memory such as read only memory (ROM) and/orrandom access memory (RAM). By way of example, and not limitation,system memory 1530 may also include an operating system, applicationprograms, other program modules, and program data.

A user can enter commands and information into the computer 1510 throughinput devices 1540, non-limiting examples of which can include akeyboard, keypad, a pointing device, a mouse, stylus, touchpad,touchscreen, trackball, motion detector, camera, microphone, joystick,game pad, scanner, or any other device that allows the user to interactwith computer 1510. A monitor or other type of display device is alsoconnected to the system bus 1522 via an interface, such as outputinterface 1550. In addition to a monitor, computers can also includeother peripheral output devices such as speakers and a printer, whichmay be connected through output interface 1550.

The computer 1510 may operate in a networked or distributed environmentusing logical connections to one or more other remote computers, such asremote computer 1570. The remote computer 1570 may be a personalcomputer, a server, a router, a network PC, a peer device or othercommon network node, or any other remote media consumption ortransmission device, and may include any or all of the elementsdescribed above relative to the computer 1510. The logical connectionsdepicted in FIG. 15 include a network 1572, such local area network(LAN) or a wide area network (WAN), but may also include othernetworks/buses e.g., cellular networks.

As mentioned above, while exemplary embodiments have been described inconnection with various computing devices and network architectures, theunderlying concepts may be applied to any network system and anycomputing device or system in which it is desirable to publish orconsume media in a flexible way.

Also, there are multiple ways to implement the same or similarfunctionality, e.g., an appropriate API, tool kit, driver code,operating system, control, standalone or downloadable software object,etc. which enables applications and services to take advantage of thetechniques described herein. Thus, embodiments herein are contemplatedfrom the standpoint of an API (or other software object), as well asfrom a software or hardware object that implements one or more aspectsdescribed herein. Thus, various embodiments described herein can haveaspects that are wholly in hardware, partly in hardware and partly insoftware, as well as in software.

The word “exemplary” is used herein to mean serving as an example,instance, or illustration. For the avoidance of doubt, the aspectsdisclosed herein are not limited by such examples. In addition, anyaspect or design described herein as “exemplary” is not necessarily tobe construed as preferred or advantageous over other aspects or designs,nor is it meant to preclude equivalent exemplary structures andtechniques known to those of ordinary skill in the art. Furthermore, tothe extent that the terms “includes,” “has,” “contains,” and othersimilar words are used in either the detailed description or the claims,for the avoidance of doubt, such terms are intended to be inclusive in amanner similar to the term “comprising” as an open transition wordwithout precluding any additional or other elements.

Computing devices typically include a variety of media, which caninclude computer-readable storage media and/or communications media, inwhich these two terms are used herein differently from one another asfollows. Computer-readable storage media can be any available storagemedia that can be accessed by the computer, is typically of anon-transitory nature, and can include both volatile and nonvolatilemedia, removable and non-removable media. By way of example, and notlimitation, computer-readable storage media can be implemented inconnection with any method or technology for storage of information suchas computer-readable instructions, program modules, structured data, orunstructured data. Computer-readable storage media can include, but arenot limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disk (DVD) or other optical diskstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or other tangible and/or non-transitorymedia which can be used to store desired information. Computer-readablestorage media can be accessed by one or more local or remote computingdevices, e.g., via access requests, queries or other data retrievalprotocols, for a variety of operations with respect to the informationstored by the medium.

On the other hand, communications media typically embodycomputer-readable instructions, data structures, program modules orother structured or unstructured data in a data signal such as amodulated data signal, e.g., a carrier wave or other transportmechanism, and includes any information delivery or transport media. Theterm “modulated data signal” or signals refers to a signal that has oneor more of its characteristics set or changed in such a manner as toencode information in one or more signals. By way of example, and notlimitation, communication media include wired media, such as a wirednetwork or direct-wired connection, and wireless media such as acoustic,RF, infrared and other wireless media.

As mentioned, the various techniques described herein may be implementedin connection with hardware or software or, where appropriate, with acombination of both. As used herein, the terms “component,” “system” andthe like are likewise intended to refer to a computer-related entity,either hardware, a combination of hardware and software, software, orsoftware in execution. For example, a component may be, but is notlimited to being, a process running on a processor, a processor, anobject, an executable, a thread of execution, a program, and/or acomputer. By way of illustration, both an application running oncomputer and the computer can be a component. One or more components mayreside within a process and/or thread of execution and a component maybe localized on one computer and/or distributed between two or morecomputers. Further, a “device” can come in the form of speciallydesigned hardware; generalized hardware made specialized by theexecution of software thereon that enables the hardware to performspecific function (e.g., coding and/or decoding); software stored on acomputer readable medium; or a combination thereof.

The aforementioned systems have been described with respect tointeraction between several components. It can be appreciated that suchsystems and components can include those components or specifiedsub-components, some of the specified components or sub-components,and/or additional components, and according to various permutations andcombinations of the foregoing. Sub-components can also be implemented ascomponents communicatively coupled to other components rather thanincluded within parent components (hierarchical). Additionally, it is tobe noted that one or more components may be combined into a singlecomponent providing aggregate functionality or divided into severalseparate sub-components, and that any one or more middle layers, such asa management layer, may be provided to communicatively couple to suchsub-components in order to provide integrated functionality. Anycomponents described herein may also interact with one or more othercomponents not specifically described herein but generally known bythose of skill in the art.

In order to provide for or aid in the numerous inferences describedherein (e.g. inferring relationships between metadata or inferringtopics of interest to users), components described herein can examinethe entirety or a subset of the data to which it is granted access andcan provide for reasoning about or infer states of the system,environment, etc. from a set of observations as captured via eventsand/or data. Inference can be employed to identify a specific context oraction, or can generate a probability distribution over states, forexample. The inference can be probabilistic—that is, the computation ofa probability distribution over states of interest based on aconsideration of data and events. Inference can also refer to techniquesemployed for composing higher-level events from a set of events and/ordata.

Such inference can result in the construction of new events or actionsfrom a set of observed events and/or stored event data, whether or notthe events are correlated in close temporal proximity, and whether theevents and data come from one or several event and data sources. Variousclassification (explicitly and/or implicitly trained) schemes and/orsystems (e.g., support vector machines, neural networks, expert systems,Bayesian belief networks, fuzzy logic, data fusion engines, etc.) can beemployed in connection with performing automatic and/or inferred actionin connection with the claimed subject matter.

A classifier can map an input attribute vector, x=(x1, x2, x3, x4, xn),to a confidence that the input belongs to a class, as byf(x)=confidence(class). Such classification can employ a probabilisticand/or statistical-based analysis (e.g., factoring into the analysisutilities and costs) to prognose or infer an action that a user desiresto be automatically performed. A support vector machine (SVM) is anexample of a classifier that can be employed. The SVM operates byfinding a hyper-surface in the space of possible inputs, where thehyper-surface attempts to split the triggering criteria from thenon-triggering events. Intuitively, this makes the classificationcorrect for testing data that is near, but not identical to trainingdata. Other directed and undirected model classification approachesinclude, e.g., naïve Bayes, Bayesian networks, decision trees, neuralnetworks, fuzzy logic models, and probabilistic classification modelsproviding different patterns of independence can be employed.Classification as used herein also is inclusive of statisticalregression that is utilized to develop models of priority.

In view of the exemplary systems described above, methodologies that maybe implemented in accordance with the described subject matter will bebetter appreciated with reference to the flowcharts of the variousfigures. While for purposes of simplicity of explanation, themethodologies are shown and described as a series of blocks, it is to beunderstood and appreciated that the claimed subject matter is notlimited by the order of the blocks, as some blocks may occur indifferent orders and/or concurrently with other blocks from what isdepicted and described herein. Where non-sequential, or branched, flowis illustrated via flowchart, it can be appreciated that various otherbranches, flow paths, and orders of the blocks, may be implemented whichachieve the same or a similar result. Moreover, not all illustratedblocks may be required to implement the methodologies describedhereinafter.

In addition to the various embodiments described herein, it is to beunderstood that other similar embodiments can be used or modificationsand additions can be made to the described embodiment(s) for performingthe same or equivalent function of the corresponding embodiment(s)without deviating there from. Still further, multiple processing chipsor multiple devices can share the performance of one or more functionsdescribed herein, and similarly, storage can be effected across aplurality of devices. Accordingly, the invention is not to be limited toany single embodiment, but rather can be construed in breadth, spiritand scope in accordance with the appended claims.

What is claimed is:
 1. A method, comprising: receiving, by a processorof a first content recording device, input indicating a synchronizedrecording request; and in response to receiving the synchronizedrecording request: identifying, by the first content recording device, aplurality of other content recording devices that meet at least onefilter criterion and that are capable of a synchronized recordingrelationship with the first content recording device; selecting, by thefirst content recording device, a second content recording device fromthe plurality of other content recording devices; establishing, by thefirst content recording device, the synchronized recording relationshipwith the second content recording device; periodically inserting, by thefirst content recording device, a first set of markers into a firstrecording at a first set of points of time while the first recording isbeing captured by the first content recording device, the first set ofmarkers being of different types, wherein the first set of markerscomprises a first content object inserted at a first point in time ofthe first set of points of time within the first recording; andinstructing, by the first content recording device, the second contentrecording device to periodically insert a second set of markers into asecond recording at a second set of points of time while the secondrecording is being captured by the second content recording device, thesecond set of markers being of different types, wherein the second setof markers comprises a second content object inserted at a second pointin time of the second set of points of time within the second recording,the first content object and the second content object being a firsttype of marker, the second point in time within the second recording andthe first point in time within the first recording correspond to acommon point in time within the first recording and the secondrecording, and the first recording and the second recording are to betemporally aligned in view of the first content object and the secondcontent object to display synchronized content comprising the firstrecording and the second recording.
 2. The method of claim 1, furthercomprising in response to the establishing the synchronized recordingrelationship with the second content recording device: initiating, bythe first content recording device, the first recording; andinstructing; by the first content recording device, the second contentrecording device to initiate the second recording.
 3. The method ofclaim 1, wherein the first content object is at least one of an audiblemarker or a visual marker, and wherein the first set of markers and thesecond set of markers are to be used in presenting the first recordingand the second recording concurrently in a merged presentation.
 4. Themethod of claim 1, wherein the at least one filter criterion comprisesat least one of a geographical parameter, a recording parameter, a userrelationship parameter, or a device type.
 5. The method of claim 4,wherein the at least one filter criterion is specified by a userassociated with the first content recording device.
 6. The method ofclaim 1 further comprising ranking the plurality of other contentrecording devices based on the at least one filter criterion, whereinthe selecting of the second content recording device from the pluralityof other content recording devices is based on the ranking.
 7. Themethod of claim 1, further comprising associating metadata to at leastone of the first recording or the second recording, wherein the metadataidentifies the synchronized recording relationship between the firstcontent recording device and the second content recording device.
 8. Afirst content recording device, comprising: a processor, communicativelycoupled to a memory that stores computer-executable components, thatexecutes or facilitates execution of the computer-executable components,comprising: an interface component to receive input indicating asynchronized recording request; and a content recording component to, inresponse to receiving the synchronized recording request: identify aplurality of other content recording devices that meet at least onefilter criterion and that are capable of a synchronized recordingrelationship with the first content recording device; select a secondcontent recording device, from the plurality of other content recordingdevices; establish the synchronized recording relationship with thesecond recording device; periodically insert a first set of markers intoa first recording at a first set of points of time while the firstrecording is being captured by the first content recording device, thefirst set of markers being of different types, wherein the first set ofmarkers comprises a first content object inserted at a first point intime of the first set of points of time within the first recording; andinstruct the second content recording device to periodically insert asecond set of markers into a second recording at a second set of pointsof time while the second recording is being captured by the secondcontent recording device, the second set of markers being of differenttypes, wherein the second set of markers comprises a second contentobject inserted at a second point in time of the second set of points oftime within the second recording, the first content object and thesecond content object being a first type of marker, the first point intime within the first recording and the second point in time within thesecond recording correspond to a common point in time within the firstrecording and the second recording, and the first recording and thesecond recording are to be temporally aligned in view of the firstcontent object and the second content object to display synchronizedcontent comprising the first recording and the second recording.
 9. Thefirst content recording device of claim 8, wherein the content recordingcomponent is further to, in response to establishing the synchronizedrecording relationship with the second content recording device:initiate the first recording; and instruct the second content recordingdevice to initiate the second recording.
 10. The first content recordingdevice of claim 8, wherein the first content object is at least one ofan audible marker or a visual marker, and wherein the first set ofmarkers and the second set of markers are to be used in presenting thefirst recording and the second recording concurrently in a mergedpresentation.
 11. The first content recording device of claim 8, whereinthe at least one filter criterion comprises at least one of ageographical parameter, a recording parameter, a user relationshipparameter, or a device type.
 12. The first content recording device ofclaim 11, wherein the at least one filter criterion is specified by auser associated with the first content recording device.
 13. The firstcontent recording device of claim 8, wherein the content recordingcomponent is further to, in response to establishing the synchronizedrecording relationship with the second content recording device, rankthe plurality of other content recording devices based on the at leastone filter criterion, wherein the content recording component is toselect the second content recording device from the plurality of othercontent recording devices based on ranking of the plurality of othercontent recording devices based on the at least one filter criterion.14. The first content recording device of claim 8, wherein the contentrecording component is further to associate metadata to at least one ofthe first recording or the second recording, wherein the metadataidentifies the synchronized recording relationship between the firstcontent recording device and the second content recording device.
 15. Anon-transitory computer-readable medium having instructions storedthereon that, in response to execution, cause a first content recordingdevice including a processor to perform operations comprising: receivinginput indicating a synchronized recording request; and in response toreceiving the synchronized recording request: identifying a plurality ofother content recording devices that meet at least one filter criterionand that are capable of a synchronized recording relationship with thefirst content recording device; selecting a second content recordingdevice from the plurality of other content recording devices;establishing the synchronized recording relationship with the secondcontent recording device; periodically inserting a first set of markersinto a first recording at a first set of points of time while the firstrecording is being captured by the first content recording device, thefirst set of markers being of different types, wherein the first set ofmarkers comprises a first content object inserted at a first point intime of the first set of points of time within the first recording; andinstructing the second content recording device to periodically insert asecond set of markers into a second recording at a second set of pointsof time while the second recording is being captured by the secondcontent recording device, the second set of markers being of differenttypes, wherein the second set of markers comprises a second contentobject inserted at a second point in time of the second set of points oftime within the second recording, the first content object and thesecond content object being a first type of marker, the second point intime within the second recording and the first point in time within thefirst recording correspond to a common point in time within the firstrecording and the second recording, and the first recording and thesecond recording are to be temporally aligned in view of the firstcontent object and the second content object to display synchronizedcontent comprising the first recording and the second recording.
 16. Thenon-transitory computer-readable medium of claim 15, the operationsfurther comprising in response to the establishing the synchronizedrecording relationship with the second content recording device:initiating the first recording; and instructing the second contentrecording device to initiate the second recording.
 17. Thenon-transitory computer-readable medium of claim 15, wherein the firstcontent object is at least one of an audible marker or a visual marker,and wherein the first set of markers and the second set of markers areto be used in presenting the first recording and the second recordingconcurrently in a merged presentation.
 18. The non-transitorycomputer-readable medium of claim 15, wherein the at least one filtercriterion comprises at least one of a geographical parameter, arecording parameter, a user relationship parameter, or a device type.19. The non-transitory computer-readable medium of claim 18, wherein theat least one filter criterion is specified by a user associated with thefirst content recording device.
 20. The non-transitory computer-readablemedium of claim 15, the operations further comprising in response to theestablishing the synchronized recording relationship with the secondcontent recording device, ranking the plurality of other contentrecording devices based on the at least one filter criterion, whereinthe selecting of the second content recording device from the pluralityof other content recording devices is based on the ranking.
 21. Thenon-transitory computer-readable medium of claim 15, the operationsfurther comprising associating metadata to at least one of the firstrecording or the second recording, wherein the metadata identifies thesynchronized recording relationship between the first content recordingdevice and the second content recording device.
 22. A first contentrecording device, comprising: a memory; and a processor, coupled to thememory, to: responsive to input indicating a synchronized recordingrequest, identify a plurality of other content recording devices thatmeet at least one filter criterion and that are capable of asynchronized recording relationship with the first content recordingdevice; select a second content recording device, from the plurality ofother content recording devices; establish the synchronized recordingrelationship with the second content recording device; periodicallyinsert a first set of markers into a first recording at a first set ofpoints of time while the first recording is being captured by the firstcontent recording device, the first set of markers being of differenttypes, wherein the first set of markers comprises a first content objectinserted at a first point in time of the first set of points of timewithin the first recording; and instruct the second content recordingdevice to periodically insert a second set of markers into a secondrecording at a second set of points of time while the second recordingis being captured by the second content recording device, the second setof markers being of different types, wherein the second set of markerscomprises a second content object inserted at a second point in time ofthe second set of points of time within the second recording, the firstcontent object and the second content object being a first type ofmarker, the second point in time within the second recording and thefirst point in time within the first recording correspond to a commonpoint in time within the first recording and the second recording, andthe first recording and the second recording are to be temporallyaligned in view of the first content object and the second contentobject to display synchronized content comprising the first recordingand the second recording.
 23. The first content recording device ofclaim 22, wherein the processor is further to, upon establishing thesynchronized recording relationship with the second content recordingdevice: initiate the first recording; and instruct the second contentrecording device to initiate the second recording.
 24. The first contentrecording device of claim 22, wherein the first content object is atleast one of an audible marker or a visual marker, and wherein the firstset of markers and the second set of markers are to be used inpresenting the first recording and the second recording concurrently ina merged presentation.
 25. The first content recording device of claim22, wherein the at least one filter criterion comprises at least one ofa geographical parameter, a recording parameter, a user relationshipparameter, or a device type.
 26. The first content recording of claim25, wherein the at least one filter criterion is specified by a userassociated with the first content recording device.
 27. The firstcontent recording device of claim 22, wherein the processor is furtherto, upon establishing the synchronized recording relationship with thesecond content recording device, rank the plurality of other contentrecording devices based on the at least one filter criterion, whereinthe processor is to select the second content recording device from theplurality of other content recording devices based on ranking of theplurality of other content recording devices based on the at least onefilter criterion.